-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Hub Generated] Review request for Microsoft.DataLakeAnalytics to add version preview/2019-11-01-preview #15893
Conversation
…e/2016-11-01 to version 2019-11-01-preview
Hi, @jimmyshie123 Thanks for your PR. I am workflow bot for review process. Here are some small tips. Any feedback about review process or workflow bot, pls contact swagger and tools team. vsswagger@microsoft.com |
Swagger Validation Report
|
Rule | Message |
---|---|
The API version:2019-11-01-preview having been in a preview state over one year , please move it to GA or retire. Location: Microsoft.DataLakeAnalytics/preview/2019-11-01-preview/account.json#L6 |
The following errors/warnings exist before current PR submission:
Only 30 items are listed, please refer to log for more details.
Rule | Message |
---|---|
R4011 - DeleteOperationResponses |
The delete operation is defined without a 200 or 204 error response implementation,please add it.' Location: Microsoft.DataLakeAnalytics/preview/2019-11-01-preview/account.json#L635 |
R4011 - DeleteOperationResponses |
The delete operation is defined without a 200 or 204 error response implementation,please add it.' Location: Microsoft.DataLakeAnalytics/preview/2019-11-01-preview/account.json#L926 |
R4018 - OperationsApiResponseSchema |
The response schema of operations API '/providers/Microsoft.DataLakeAnalytics/operations' does not match the ARM specification. Please standardize the schema. Location: Microsoft.DataLakeAnalytics/preview/2019-11-01-preview/account.json#L1617 |
R4019 - GetCollectionResponseSchema |
The response in the GET collection operation 'Accounts_List' does not match the response definition in the individual GET operation 'Accounts_Get' . Location: Microsoft.DataLakeAnalytics/preview/2019-11-01-preview/account.json#L36 |
R4032 - MissingXmsErrorResponse |
Response code 404 is defined without a x-ms-error-response. Location: Microsoft.DataLakeAnalytics/preview/2019-11-01-preview/account.json#L1679 |
R4037 - MissingTypeObject |
The schema 'Resource' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.DataLakeAnalytics/preview/2019-11-01-preview/account.json#L1750 |
R4037 - MissingTypeObject |
The schema 'SubResource' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.DataLakeAnalytics/preview/2019-11-01-preview/account.json#L1784 |
R4037 - MissingTypeObject |
The schema 'DataLakeAnalyticsAccount' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.DataLakeAnalytics/preview/2019-11-01-preview/account.json#L1805 |
R4037 - MissingTypeObject |
The schema 'DataLakeAnalyticsAccountBasic' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.DataLakeAnalytics/preview/2019-11-01-preview/account.json#L1821 |
R4037 - MissingTypeObject |
The schema 'DataLakeAnalyticsAccountProperties' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.DataLakeAnalytics/preview/2019-11-01-preview/account.json#L1837 |
R4037 - MissingTypeObject |
The schema 'DataLakeAnalyticsAccountPropertiesBasic' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.DataLakeAnalytics/preview/2019-11-01-preview/account.json#L2054 |
R4037 - MissingTypeObject |
The schema 'DataLakeAnalyticsAccountListResult' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.DataLakeAnalytics/preview/2019-11-01-preview/account.json#L2117 |
R4037 - MissingTypeObject |
The schema 'DataLakeStoreAccountInformation' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.DataLakeAnalytics/preview/2019-11-01-preview/account.json#L2135 |
R4037 - MissingTypeObject |
The schema 'DataLakeStoreAccountInformationProperties' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.DataLakeAnalytics/preview/2019-11-01-preview/account.json#L2150 |
R4037 - MissingTypeObject |
The schema 'DataLakeStoreAccountInformationListResult' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.DataLakeAnalytics/preview/2019-11-01-preview/account.json#L2160 |
R4037 - MissingTypeObject |
The schema 'StorageAccountInformation' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.DataLakeAnalytics/preview/2019-11-01-preview/account.json#L2178 |
R4037 - MissingTypeObject |
The schema 'StorageAccountInformationProperties' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.DataLakeAnalytics/preview/2019-11-01-preview/account.json#L2194 |
R4037 - MissingTypeObject |
The schema 'StorageAccountInformationListResult' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.DataLakeAnalytics/preview/2019-11-01-preview/account.json#L2204 |
R4037 - MissingTypeObject |
The schema 'StorageContainer' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.DataLakeAnalytics/preview/2019-11-01-preview/account.json#L2222 |
R4037 - MissingTypeObject |
The schema 'StorageContainerProperties' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.DataLakeAnalytics/preview/2019-11-01-preview/account.json#L2238 |
R4037 - MissingTypeObject |
The schema 'StorageContainerListResult' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.DataLakeAnalytics/preview/2019-11-01-preview/account.json#L2249 |
R4037 - MissingTypeObject |
The schema 'SasTokenInformation' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.DataLakeAnalytics/preview/2019-11-01-preview/account.json#L2267 |
R4037 - MissingTypeObject |
The schema 'SasTokenInformationListResult' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.DataLakeAnalytics/preview/2019-11-01-preview/account.json#L2277 |
R4037 - MissingTypeObject |
The schema 'ComputePolicy' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.DataLakeAnalytics/preview/2019-11-01-preview/account.json#L2295 |
R4037 - MissingTypeObject |
The schema 'ComputePolicyProperties' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.DataLakeAnalytics/preview/2019-11-01-preview/account.json#L2311 |
R4037 - MissingTypeObject |
The schema 'ComputePolicyListResult' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.DataLakeAnalytics/preview/2019-11-01-preview/account.json#L2350 |
R4037 - MissingTypeObject |
The schema 'FirewallRule' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.DataLakeAnalytics/preview/2019-11-01-preview/account.json#L2368 |
R4037 - MissingTypeObject |
The schema 'FirewallRuleProperties' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.DataLakeAnalytics/preview/2019-11-01-preview/account.json#L2384 |
R4037 - MissingTypeObject |
The schema 'FirewallRuleListResult' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.DataLakeAnalytics/preview/2019-11-01-preview/account.json#L2399 |
R4037 - MissingTypeObject |
The schema 'VirtualNetworkRule' is considered an object but without a 'type:object', please add the missing 'type:object'. Location: Microsoft.DataLakeAnalytics/preview/2019-11-01-preview/account.json#L2431 |
️️✔️
Avocado succeeded [Detail] [Expand]
Validation passes for Avocado.
️️✔️
ModelValidation succeeded [Detail] [Expand]
Validation passes for ModelValidation.
️️✔️
SemanticValidation succeeded [Detail] [Expand]
Validation passes for SemanticValidation.
️⚠️
Cross-Version Breaking Changes: 52 Warnings warning [Detail]
- Compared Swaggers (Based on Oad v0.9.0)
- current:preview/2019-11-01-preview/account.json compared with base:stable/2016-11-01/account.json
- current:preview/2019-11-01-preview/account.json compared with base:preview/2015-10-01-preview/account.json
Only 30 items are listed, please refer to log for more details.
️️✔️
CredScan succeeded [Detail] [Expand]
There is no credential detected.
️️✔️
[Staging] SDK Track2 Validation succeeded [Detail] [Expand]
Validation passes for SDKTrack2Validation
- The following tags are being changed in this PR
️️✔️
[Staging] PrettierCheck succeeded [Detail] [Expand]
Validation passes for PrettierCheck.
️️✔️
[Staging] SpellCheck succeeded [Detail] [Expand]
Validation passes for SpellCheck.
️️✔️
[Staging] Lint(RPaaS) succeeded [Detail] [Expand]
Validation passes for Lint(RPaaS).
Swagger Generation Artifacts
|
[Call for Action] To better understand Azure service dev/test scenario, and support Azure service developer better on Swagger and REST API related tests in early phase, please help to fill in with this survey https://aka.ms/SurveyForEarlyPhase. It will take 5 to 10 minutes. If you already complete survey, please neglect this comment. Thanks. |
Hi, @jimmyshie123 your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board(armapireview@microsoft.com). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Signed off from ARM side.
…rosoft.DataLakeAnalytics to add version preview/2019-11-01-preview (#1902) Create to sync Azure/azure-rest-api-specs#15893 [ReCreate this PR](https://github.com/azure-resource-manager-schemas/compare/main...AzureSDKAutomation:sdkAuto/datalake-analytics?expand=1)
… version preview/2019-11-01-preview (Azure#15893) * Adds base for updating Microsoft.DataLakeAnalytics from version stable/2016-11-01 to version 2019-11-01-preview * Updates readme * Updates API version in new specs and examples * test validation patch Co-authored-by: Jimmy Xie <jimmyxie@microsoft.com>
This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
Changelog
Add a changelog entry for this PR by answering the following questions:
Contribution checklist:
If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist
Otherwise your PR may be subject to ARM review requirements. Complete the following:
Check this box if any of the following apply to the PR so that label “WaitForARMFeedback” will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits.
Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.
If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.